Bugs, A.Net? - Guild Wars Forums

OI-812 · Jun 23, 2007, 06:44 PM // 18:44

How long does it usually take for A.Net to fix confirmed bugs? I mean, they programmed the game... They have the "blueprints", they know it inside out, so why isn't fixing bugs a simple matter of shutting down the server for a bit, going in, fixing the problem, and bringing things back online? Are they waiting for a bunch of them to pile up so they can knock a bunch out all at once? I was under the impression that A.Net was able to constantly patch GW as needed, on the fly (just requires a log-out/log-in by the player). What takes them so long? What is involved in the process of amending a bug? I might have a better appreciation for their job if they'd tell me exactly what it is they're doing that makes it so complex, and thus time-consuming. I don't understand. Help me understand, A.Net.

JeniM · Jun 23, 2007, 07:07 PM // 19:07

I have always found Anet fix a bug they make in an update within the day

As for the bugs that have been here for ages no idea if they will ever be fixed

zwei2stein · Jun 23, 2007, 07:15 PM // 19:15

(know how of generic code monkey

* Bug must be noticed - be it by reading on forums or throught support questios or when boss tried to do something and software crashed.
* Bug must be verified that it really exists. That means that someone gives it to QA team and that team tries to replicate bug.
* After that its is given rank - from severe bugs that must be fixed asap to minor bugs that are being fixed if programer has nothing better to do (aka, never).
* Once programer get green light to do it (or is waken up in middle of might by angry phonecall), he must get familiar with what is going on.
* Even if you wrote code and know how it works, bugs is usually hard to find (if you knew where to look and what is wrong, you wouldnt make that bug to being with)
* When problem is identified, it can be very trivial to repair (small typo) or very VERY complex (requiring rewrite of huge pile of code and carefull examination of related code)
* When bug is fixed, software must be tested thoroughly. It is very common that fixing bug produces another or that it disrupts some related fuctionality, if something like that happens, return few steps back and repeat.

* Sometimes bugs need multi-person cooperation (i would say that, i.e. npc getting stuck in early factions i nvarious missions required interaction of programer who wrote pathfinding and of level deisgner.), that can be time consuming and unproductiove (you must have sure all people have time to cooperate.)

OI-812 · Jun 23, 2007, 07:29 PM // 19:29

But when GW techs are at work, they are actually WORKING, right? When they're on the clock, they are sitting there and poring through the bug info, and attempting to resolve them, right? How many techs are there on the job at any one point in time? What else are the programmers doing? Prepping GW for the addition of GW:EN? Wouldn't it make more sense to get the knots out of the string of christmas lights you already have before adding another string of lights (to use a really poor analogy)?

wetsparks · Jun 23, 2007, 07:34 PM // 19:34

Quote:

Originally Posted by zwei2stein

* When bug is fixed, software must be tested thoroughly. It is very common that fixing bug produces another or that it disrupts some related fuctionality, if something like that happens, return few steps back and repeat.

It is not uncommon for companies to intentionally leave bugs in games for that reason. Fixing the one bug may trigger five other bugs or one bug that is game breaking and push production back a couple months.

Loviatar · Jun 23, 2007, 07:50 PM // 19:50

Quote:

Originally Posted by OI-812

But when GW techs are at work, they are actually WORKING, right? When they're on the clock, they are sitting there and poring through the bug info, and attempting to resolve them, right? How many techs are there on the job at any one point in time? What else are the programmers doing? Prepping GW for the addition of GW:EN? Wouldn't it make more sense to get the knots out of the string of christmas lights you already have before adding another string of lights (to use a really poor analogy)?

as has been officially explained before they have several SERARATE teams which are kept in constant update with each other

including a separate events/holiday team

including a bug swat team.

WHAT BUG HAS YOU IN A TIZZY?

OI-812 · Jun 23, 2007, 08:09 PM // 20:09

Quote:

Originally Posted by wetsparks

It is not uncommon for companies to intentionally leave bugs in games for that reason. Fixing the one bug may trigger five other bugs or one bug that is game breaking and push production back a couple months.

Kind of like a demented game of computer-code Jenga?

I will say this, Guild Wars has far fewer game-breaking bugs than Dark Age of Camelot ever did...

Quote:

WHAT BUG HAS YOU IN A TIZZY?

At the moment the only bug I'm having a problem with is almost certainly my computer's fault... but I read the Game Bugs forum, and the Outstanding Bugs thread, and I got to wondering, that's all.

Jun 23, 2007, 06:44 PM // 18:44	#1
OI-812 Lion's Arch Merchant Join Date: Apr 2006 Location: Somewhere between GW and Fchan on the nets Guild: None Profession: R/D	Bugs, A.Net? How long does it usually take for A.Net to fix confirmed bugs? I mean, they programmed the game... They have the "blueprints", they know it inside out, so why isn't fixing bugs a simple matter of shutting down the server for a bit, going in, fixing the problem, and bringing things back online? Are they waiting for a bunch of them to pile up so they can knock a bunch out all at once? I was under the impression that A.Net was able to constantly patch GW as needed, on the fly (just requires a log-out/log-in by the player). What takes them so long? What is involved in the process of amending a bug? I might have a better appreciation for their job if they'd tell me exactly what it is they're doing that makes it so complex, and thus time-consuming. I don't understand. Help me understand, A.Net.

Jun 23, 2007, 07:07 PM // 19:07	#2
JeniM Desert Nomad Join Date: May 2007 Profession: W/E	I have always found Anet fix a bug they make in an update within the day As for the bugs that have been here for ages no idea if they will ever be fixed

Jun 23, 2007, 07:15 PM // 19:15	#3
zwei2stein Grotto Attendant Join Date: Jun 2006 Location: Europe Guild: The German Order [GER] Profession: N/	(know how of generic code monkey * Bug must be noticed - be it by reading on forums or throught support questios or when boss tried to do something and software crashed. * Bug must be verified that it really exists. That means that someone gives it to QA team and that team tries to replicate bug. * After that its is given rank - from severe bugs that must be fixed asap to minor bugs that are being fixed if programer has nothing better to do (aka, never). * Once programer get green light to do it (or is waken up in middle of might by angry phonecall), he must get familiar with what is going on. * Even if you wrote code and know how it works, bugs is usually hard to find (if you knew where to look and what is wrong, you wouldnt make that bug to being with) * When problem is identified, it can be very trivial to repair (small typo) or very VERY complex (requiring rewrite of huge pile of code and carefull examination of related code) * When bug is fixed, software must be tested thoroughly. It is very common that fixing bug produces another or that it disrupts some related fuctionality, if something like that happens, return few steps back and repeat. * Sometimes bugs need multi-person cooperation (i would say that, i.e. npc getting stuck in early factions i nvarious missions required interaction of programer who wrote pathfinding and of level deisgner.), that can be time consuming and unproductiove (you must have sure all people have time to cooperate.)

Jun 23, 2007, 07:29 PM // 19:29	#4
OI-812 Lion's Arch Merchant Join Date: Apr 2006 Location: Somewhere between GW and Fchan on the nets Guild: None Profession: R/D	But when GW techs are at work, they are actually WORKING, right? When they're on the clock, they are sitting there and poring through the bug info, and attempting to resolve them, right? How many techs are there on the job at any one point in time? What else are the programmers doing? Prepping GW for the addition of GW:EN? Wouldn't it make more sense to get the knots out of the string of christmas lights you already have before adding another string of lights (to use a really poor analogy)?